-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x-pack/filebeat/module/cisco: remove invalid values from ECS fields #31628
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This prevents "monitored" from being written into event.outcome which does not allow this value according to ECS.
efd6
added
bug
Filebeat
Filebeat
Team:Security-External Integrations
Integration:Cisco
8.3-candidate
backport-v8.2.0
Automated backport with mergify
labels
May 16, 2022
botelastic
bot
added
needs_team
Indicates that the issue/PR needs a Team:* label
and removed
needs_team
Indicates that the issue/PR needs a Team:* label
labels
May 16, 2022
efd6
commented
May 16, 2022
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
Collaborator
adriansr
approved these changes
May 16, 2022
efd6
added a commit
that referenced
this pull request
May 16, 2022
…31628) (#31634) This prevents "monitored" from being written into event.outcome which does not allow this value according to ECS. (cherry picked from commit 5a4bfca) Co-authored-by: Dan Kortschak <[email protected]>
agithomas
added a commit
to agithomas/beats
that referenced
this pull request
May 18, 2022
…lastic#31628) This prevents "monitored" from being written into event.outcome which does not allow this value according to ECS.
agithomas
added a commit
to agithomas/beats
that referenced
this pull request
Nov 3, 2022
…lastic#31628) This prevents "monitored" from being written into event.outcome which does not allow this value according to ECS.
chrisberkhout
pushed a commit
that referenced
this pull request
Jun 1, 2023
…31628) This prevents "monitored" from being written into event.outcome which does not allow this value according to ECS.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
8.3-candidate
backport-v8.2.0
Automated backport with mergify
bug
Filebeat
Filebeat
Integration:Cisco
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This prevents "monitored" from being written into event.outcome which
does not allow this value according to ECS.
Why is it important?
This brings the generated documents into conformance with ECS.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs